Automatically detecting and storing digital data items associated with digital calendar items

ABSTRACT

A computer-implemented method comprises, obtaining a digital calendar item for an event, determining, that the event has begun, and in response to determining that the event has begun, accessing a location and determining which of the participants are present for the event, determining, during the event, that one participant shared a digital data item with the other participants or as part of the event, and in response to determining that the participant shared the digital data item, at least transiently storing a reference or link to the digital data item, determining that the event has ended, and in response to determining that the event has ended, updating the digital calendar item by adding the reference or link.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a continuation patent application of U.S. patentapplication Ser. No. 16/773,904, filed Jan. 27, 2020 and titled“Automatically Detecting and Storing Digital Data Items Associated withDigital Calendar Items,” which is a continuation patent application ofU.S. patent application Ser. No. 16/125,382, filed Sep. 7, 2018 andtitled “Automatically Detecting and Storing Digital Data ItemsAssociated with Digital Calendar Items,” now U.S. Pat. No. 10,579,970,which is a nonprovisional patent application of and claims the benefitof U.S. Provisional Patent Application No. 62/555,595, filed Sep. 7,2017 and titled “Automatically Detecting and Storing Digital Data ItemsAssociated with Digital Calendar Items,” the disclosures of which arehereby incorporated herein by reference in their entireties.

FIELD

The present disclosure generally relates to improved systems, methods,computer software and hardware in the field of enterprise productivityapplications. The disclosure relates more specifically to improvedcomputer-implemented systems and methods for automatically detecting andstoring digital data items that are associated with digital calendaritems or meetings that occur in response to digital calendar items.

BACKGROUND

The approaches described in this background section are not necessarilyprior art to the claims in this application and are not admitted asprior art by inclusion in this section.

Computer programs implementing productivity applications are ubiquitous.Examples of productivity applications include word processingapplications, email clients, spreadsheet applications, issue trackingsoftware, calendar or scheduling applications, messaging applications,audio/video conferencing applications, and many others. Calendarapplications or calendar functionality have become essential to therunning of a modern business. Employees need to be able to scheduleevents, such as a meeting, with other employees, outside vendors, andother collaborators. Although much advancement has been made in otherareas of productivity applications, calendar applications that improvethe efficiency of scheduled meetings have seen only limited development.

For example, the calendar items themselves are simple and relativelystatic. Once a calendar item is created for an event, the item remainsmore or less static aside from RSVP information, despite theavailability of digital data items, such as presented or shareddocuments, that relate to the scheduled meeting or event. A particularproblem to be solved in the present invention is the inefficiencyinvolved in a user searching for documents, messages, videos,recordings, or other digital content associated with a meeting that hasoccurred.

SUMMARY

This disclosure describes computer-implemented techniques for bindingelectronic documents, messages, chat room conversations, videos,recordings or other content to an event that is represented in acalendar item such as a meeting, based on detecting what content theparticipants in the meeting interact with during the meeting. Forexample, one approach involves obtaining a calendar item for an event,where the calendar item has time data, location data, and participantdata for each of a plurality of participants. In response to determiningthat the event has started, the location data is used to determine whichof the participants are present for the event. Retrieving account dataor geo-location data for devices of participants could be used to verifylocation or presence. During the event, when a participant shares acontent item with the other participants or with a meeting service, areference or link to the content item is recorded. When the event ends,the calendar item may be updated to add the reference or link for allcontent items that were shared. Or, an event such as a video conferencemay occur separately from the calendar item yet could involveinteractions with content items that are relevant to the calendar item;in such a case, the content items may be detected automatically andreferences to the content items may be updated in the calendar item.

In this manner, meetings or other events represented by calendar itemsautomatically acquire references to materials that were used during theevents represented in the calendar items or in other related events.Events or calendar items then may include an event name, identificationof participants in the event, and an aggregation of all activities andreferences that occurred in the meeting. These techniques potentiallygreatly reduce the need for follow-up communications betweenparticipants to find the materials that were used. Furthermore, thetechniques automatically consolidate virtually all electronic resourcesthat were or should be associated with an event for rapid retrieval anduse at times after the event.

In addition, the appended claims may serve as a summary of theinvention.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings:

FIG. 1 illustrates a computer system in accordance with an embodiment ofthe invention.

FIG. 2 illustrates a data processing algorithm or method in accordancewith an embodiment of the invention.

FIG. 3 illustrates example digital calendar items in accordance with anembodiment of the invention.

FIG. 4 shows a block diagram of a computer system with which anembodiment of the invention may be implemented.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of the present invention. It will be apparent, however,that the present invention may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form to avoid unnecessarily obscuring the presentinvention. Embodiments are described in sections according to thefollowing outline:

-   -   1. OVERVIEW    -   2. EXAMPLE SYSTEM IMPLEMENTATION    -   3. EXAMPLE FUNCTIONAL IMPLEMENTATION    -   4. IMPLEMENTATION EXAMPLE    -   5. IMPLEMENTATION EXAMPLE—HARDWARE OVERVIEW    -   6. EXTENSIONS AND ALTERNATIVES

1. Overview

Computer-implemented techniques are provided for automatically detectingand storing digital data items associated with calendar items. In oneembodiment, a calendar item for an event is obtained. The calendar itemmay include time data, location data and participant data. Time data maycomprise a start time and an end time for the event. The location datamay identify a physical or virtual location where the event will beheld. The physical or virtual location may comprise a video conferenceroom or link, a virtual room in a video conferencing application, aphone number, an audio conferencing application or audio meetinglocation, any other application for sharing, viewing or editing ofcontent across collaborators, or a room. The participant data mayidentify the participants who are invited to attend the event orincluded in the event; account identifiers, handles or user identifiersmay be used in various embodiments. A calendar item may represent anevent in a calendar application program or productivity applicationprogram. In other cases, an event may occur separate from a calendaritem; for example, a meeting could be represented in a calendar item,but communication via video conference could occur separately and at adifferent time and physical or virtual place, yet involve content thatis relevant to the meeting. Thus, an event may refer to any occurrenceof communication between two or more computers, accounts or individualsthat is facilitated in part by electronic communication. Examplesinclude but are not limited to: a meeting, conference, seminar, set ofe-mail messages or thread, forum postings, electronic chat messages,telephone or video conferences or calls, etc.

After determining the event associated with the calendar item has begun,for example, because the start time for the calendar item has beenreached or because the scheduled meeting in the video conferenceapplication associated with the calendar item has been started by themoderator, location data and participant data associated with thecalendar item may be accessed. For example, the assigned meeting in avideo conference application may be accessed and a list of participantswho have joined the video conference meeting or are shown as a meetingattendee on the calendar item may be accessed. During the event, dataitems that are shared, created, used, or otherwise accessed are detectedand stored. Examples of data items include electronic documents, audiorecordings, video recordings, chat logs, emails, screen sharing,identities of participants that attended the event, identities ofparticipants that did not attend the event, metadata, etc. For example,a document shared on screen during a video conference meeting may bedetected and stored. But the data items are not limited to those sharedvia a video conference or audio conference application, and may includeitems such as emails or chat messages exchanged between participantsoutside of a video or audio conference location associated with theevent and documents created on other productivity application by eventparticipants during the event, such as a sketch drawn on an electronicwhite board application. Further, data items may also be detected in thetime immediately before or after the event, depending on settings thatmay be adjusted.

After the event is determined to be concluded, the data items storedduring the event are processed. Processing may be done in parallel, mayinvolve different steps or actions, and may be performed by differentcomponents, depending on the particular data item. For example, if oneof the data items is a video recording or an audio recording, then thedata item may be transcribed to generate a transcript. After thetranscript is generated, the transcript may be updated to identifyspeakers using the participant data, add timestamps, add whenparticipants entered or left the location associated with the event, addparticipant contact information, add links to shared data items andtimestamps for when the data items were shared, add links to participantchat handles or email, metadata, or enrich the transcript in any otherway. Additionally, the transcript, video recording, audio recording, orother data items may be used to identify tasks or action items assignedto participants or other individuals. Any identified tasks or actionitems may then be used to generate a ticket or data item in a projectmanagement application, issue tracking or other application, generate anew calendar item for the participant assigned the task or action, sendnotifications, or perform any other action.

As another example, if the data item is a document shared during theevent, then any changes made to the document during the event may beidentified, and multiple versions or views of the document may begenerated, such as an original version, a modified version, and a listof changes. As another example, the collected data items may be filteredto reduce the total amount of data items or content and to keep thefocus on the topic of the meeting. Thus, if ten data items were storedbecause of the event, the ten data items may be reduced to the mostrelevant three data items by filtering. Many other actions may also betaken, as discussed below.

After processing, the original calendar item is updated with any of theavailable data. For example, the participants may be updated to reflectwho actually attended the event, when they arrived, and when they left.Further, the collected data items may be added, linked, or attached tothe calendar item. Thus, the calendar item becomes a vastly more usefultool as the context and results of the event are made readily availableto the participants, improving the results of the event. Alternatively,or in addition, the data items may be made available at anotherlocation. Further, notifications may be sent to the participantsalerting them to the updated calendar item, or for any other reason.

Other aspects, features and embodiments will become apparent from thedisclosure as a whole. Throughout the disclosure, the terms “data item”and “calendar item” refer to digital data that may be stored inelectronic digital data storage devices and may be manipulated bycomputer processors and this disclosure is not intended to cover orclaim abstract concepts. The described embodiments provide significantimprovements to the usability of digital calendars and computing devicesthat interact with calendars and data items, in particular forautomatically detecting and storing data items that are associated withcalendar items or meetings that occur in response to calendar items.These techniques offer, in addition to improved user experience, reducedusage of network bandwidth, CPU cycles, storage, and/or memory becauseof the efficiency of the algorithms that are disclosed.

2. Example Computer System Implementation

FIG. 1 illustrates an example computer system in which the techniquesdescribed may be practiced, according to some embodiments.

In one embodiment, a computer system 100 comprises components that areimplemented at least partially by hardware at one or more computingdevices, such as one or more hardware processors executing storedprogram instructions stored in one or more memories for performing thefunctions that are described herein. In other words, all functionsdescribed herein are intended to indicate operations that are performedusing programming in a special-purpose computer or general-purposecomputer, in various embodiments. FIG. 1 illustrates only one of manypossible arrangements of components configured to execute theprogramming described herein. Other arrangements may include fewer ordifferent components, and the division of work between the componentsmay vary depending on the arrangement.

The computer system 100 of FIG. 1 includes server computer 105, eventapplication 110, data storage device 115, calendar item 120, data item125, client device 130, and applications 135. In one embodiment, servercomputer 105 may be a multitenant service provider computer owned by,operated by, or associated with an application service provider thatprovides an online, real-time application program based upon software asa service (SaaS) environment that is used by or accessible to multipletenants, and accessed using client computers coupled over one or morenetworks to server computer 105.

Alternatively, server computer 105 may be any computing device, and maybe owned or operated on the behalf of a single entity, such as a behindthe firewall server for a business. Server computer 105 iscommunicatively connected to data storage device 115 and client device130 using any suitable wired or wireless connection, including, but notlimited to: a Local Area Network (LAN), a Wide Area Network (WAN), theInternet, a company network, etc. Server computer 105 executes eventapplication 110. Additionally, server computer may execute additionalapplications (not shown) in addition to event application 110.

In one embodiment, data storage device 115 may be any suitable storagedevice such as one or more hard disk drives, memories, or any otherelectronic digital data recording device configured to store data.Although data storage device 115 is depicted as a single device in FIG.1 , data storage device 115 may span multiple devices located in one ormore physical locations. For example, data storage device 115 may be oneor more nodes of one or more data warehouse(s). Additionally, in oneembodiment, data storage device 115 may be located on the same device(s)as server computer 105. Alternatively, data storage device 115 may belocated on a separate device(s) from server computer 105. Additionally,data storage devices may be located on each client device associatedwith a computing system, such as an enterprise or work computing system.Any combination of the above may be used.

Data storage device 115 may include one or more databases implementedusing any suitable methodology, such as a relational database, acolumnar database, etc. The database may be of any size, portioned intoany number of rows, columns, or tables, and may be organized in anymanner. In a multitenant embodiment, data stored on data storage device115 may relate to any number of different tenants, such as hundreds tothousands of tenants or more depending on resource capacity andthroughput. The data stored on data storage device 115 may relate to anytype of data, such as chat or messaging application data, calendarapplication data, productivity application data, email application data,personal information, business information, governmental data, healthdata, environmental data, or police or military data. Individual datarecords may have any number of fields, components, or other aspects.

In one embodiment, data storage device 115 stores calendar item 120.Calendar item 120 may be created, used, accessed by, or otherwiseassociated with one or more applications or functionality withinapplications. For example, calendar item 120 may be associated with anemail application with built in calendar or schedule functionality.Alternatively, calendar item 120 may be associated with a module orfunction of a chat application that enables calendaring or schedulingamongst the users of the chat client. Further still, calendar item 120may be associated with a web-based application that includes or providescalendaring or scheduling functionality. In one embodiment, eventapplication 110 may provide calendaring or scheduling functionality, butthis capability is not required. The calendar item 120 may be associatedwith, used by, or created by any application.

Calendar item 120 comprises a programmatic object, database record,dataset or record representing or associated with an event that has beencreated and stored. As mentioned above, the event may refer to anyoccurrence of communication between two or more computers, accounts orindividuals that is facilitated in part by electronic communication,including but not limited to: a meeting, conference, seminar, set ofe-mail messages or thread, forum postings, electronic chat messages,telephone or video conferences or calls, etc. Calendar item 120 mayinclude any information needed by or useful to the invited participantsof the event including, but not limited to: time data such as a date, astart time, and an end time, location data such as a video conferencelink, an audio conference link, a phone number, and a physical roomnumber, participant data such as first name, last name, email address,chat handle, phone number, physical location, and other identifyinginformation, attachments such as a document for discussion or reference,and an agenda. As discussed below, calendar item 120 is updated by eventapplication 110 after the event has concluded to provide additionaldetails about what transpired during the event and improve the resultsof the event.

In one embodiment, data item 125 may be any item or items of digitaldata. Any number of data items 125 may be stored by data storage device115. Data item 125 may be a copy of digital data, an original of digitaldata, or may be a link to a location where a particular data item 125may be accessed or is stored. A particular data item 125 is associatedwith a particular calendar item 120 by being created, modified, shared,used, or otherwise accessed by one or more participants during an eventthat is associated with a particular calendar item 120.

Additionally, a data item 125 may be created or modified after an eventhas concluded, such as by event application 110 as part of processingother data items 125. Thus, data item 125 may be any item or items ofdigital data including, but not limited to: Universal Resource Locators(URLs), a website, emails, chat logs, a text or short message service(SMS) message, an audio recording, a video recording, a transcript, atext document, a spreadsheet, source code, a slideshow, pictures orother images, electronic data file(s), metadata, etc.

Returning to server computer 105, in one embodiment, server computer 105executes event application 110. Although depicted in FIG. 1 as a singlestandalone application, event application 110 may be one or moreapplications, plugins, and/or modules that execute on one or morecomputing devices. In some embodiments, application 110 is programmed orconfigured to obtain a calendar item 120 for an event. The calendar itemmay be obtained by accessing a database or data storage device wherecalendar items are stored. In other embodiments, obtaining and updatingcalendar items with references to data items, content items or mediadata may be performed by a program, process, service or other softwareelement that is separate from the event application 110 and executes onthe same server computer 105 or a different computer.

Alternatively, or in addition, the calendar item may be obtained when aparticipant or application notifies event application 110 of thecalendar item 120, such as by inviting an alias associated with eventapplication 110 as a participant of the event or by any other way. Eventapplication 110 may automatically detect when a user creates a calendaritem or receives a calendar item as an invitation to an event. Onceobtained, event application 110 may process calendar item 125 toidentify any needed information, such as a start date and time.

In other embodiments, multiple kinds of event applications 110 mayexecute on the server computer 105 or multiple computers, and each kindof event application may independently create event records 112 forevents associated with that event application or may create and managethe calendar item 120. Or, multiple calendar items 120 may be created atdifferent times and associated with one another via internal referencesor links. For example, a first kind of event application 110 could be avideo conferencing application that creates event records 112 of videoconferences that have been scheduled; the video conferences may beassociated with or relate to a particular calendar item 120 using a linkthat is created by the first kind of event application, but are notnecessarily represented by the calendar item. As a specific example, thecalendar item 120 could represent a scheduled voice conference betweenAlice, Bob and Charles on Jan. 15, 2020, but the event record 112 couldrepresent a video conference between Alice and Bob occurring on Jan. 5,2020 in which Alice and Bob review an agenda for the January 15 meeting;thus, the calendar item and event record may be related, but need notrepresent the same real-word occurrence. Programmatic links, URLs, URIsor other references may be stored in an event record 112 to associate itwith a calendar item 120.

Event application 110 is programmed or configured to determine that anevent has begun and to access a location associated with the event. Thedetermination that an event has begun may be made by comparing a currenttime, based on a system clock of the server computer 105, with the eventstart time in the calendar item. The location of the event may beaccessed in any suitable manner. Event application 110 may be the hostof a video conference or audio conference, may be invited as aparticipant, or may access the location using an Application ProgrammingInterface (API), or other programmatic methods. Alternatively, eventapplication 110 may access the location via a plugin or module of adifferent application running on a computing device of one or moreparticipants of the event. If the event location is a phone number, thephone number may be dialed. Optionally, the location associated with theevent may be accessed slightly before the event begins.

Event application 110 is programmed or configured to determineparticipants present for the event. The present participants may bedetermined in any suitable manner. For example, the participants may beidentified using names, handles, or other identifiers entered when theparticipants accessed the location associated with the event or joinedthe event. These identifiers may be compared with the list ofparticipants in the calendar item. Alternatively, or in addition, theidentifiers may be compared with a contact list, such as a company-wideemployee directory or other list, or contact lists of otherparticipants. In this way, participants that are not listed in calendaritem may be identified.

Additional information may be determined for the participants, such as ajoin time and a leave time, metadata, or any other information. In oneembodiment, event application 110 may cause the present participants tobe determined by another application, such as by an application hostingthe event, and may receive the identified participants as data items inany format at any time.

Event application 110 is programmed or configured to detect and storemedia data and data items from the event. The media data and data itemsmay be detected in any manner, and may be stored in any manner at anylocation. In particular, media data may be a video recording, audiorecording, chat log, or any combination thereof. The media data may berecorded or collected in any manner, by any component, such as eventapplication 110, a different application, or an application, plugin, ormodule executing on a computing device of a participant. The media datais itself a data item, and may be stored on data storage device 115 inany format. Data items may be detected by monitoring the actions ofparticipants of the event, and creating copies of any data itemscreated, shared, used, or otherwise accessed during the event.

Alternatively, or in addition, locations where the data items may beaccessed may be identified and links to the data items may be stored.Optionally, the monitoring may continue for a short period before and/orafter the event, so that additional data items may be collected. Forexample, an email may be detected and stored as a data item when theemail is sent from one participant of an event to another participant ofthe event during the event, or in the time immediately before or afterthe event. As another example, documents opened or modified during ascreen share may be detected and stored as data items. Likewise, if aparticipant of an event prints a document during the event, the digitalversion of the printed document may be detected as a data item andstored.

The quantity of information detected and stored by event application 110may be adjusted by individual users, administrators, programmers, orother suitable entities as desired to ensure that the participants havean appropriate level of privacy. For example, the attributes that may beadjusted include, but are not limited to: the duration of detection,types of digital data files detected, a security or clearance levelassociated with digital data files may be considered, or any other wayof tailoring the detection and storage of data items.

Further, all information detected and stored does not need to beincluded in any update of the calendar item. As discussed below, thestored information may be filtered to ensure that relevant items areincluded, and that irrelevant items are excluded. Optionally, approvalby an author or approval by participants associated with a data item maybe required before the data item is shared with other participants.

Event application 110 is programmed or configured to determine an eventhas concluded. The determination may be made in any suitable manner. Forexample, the determination may be based on the end time of an eventoccurring. Alternatively, the end time may be determined based on whenone or more participants have left the location associated with theevent, as indicated by location data associated with mobile computingdevices. This approach may be appropriate when an event ends early orruns long. The determination is stored so that the actual end time ofthe event may be used to update the calendar item, as discussed below.

Event application 110 is programmed or configured to transcribe or causetranscribing of media data to generate a transcript. The transcriptionmay be performed by event application 110, or may be performed by aseparate application or service. For example, event application 110 mayautomatically send an audio or video recording to a transcriptionservice, and receive a completed transcription back in an amount oftime, such as one day. Regardless of how the transcript is generated,the transcript may be in any format, such as a text file.

Event application 110 is programmed or configured to update a generatedtranscript. The transcript may be updated with any availableinformation. For instance, if speakers are identified in the transcript,the names of speakers may be checked against the known list ofparticipants and corrected as necessary. If speakers are not identified,they may be added using available metadata or other data (such as byusing timestamps and who a dominant or active speaker in a videorecording was). Further, the names of speakers may be updated intoclickable links that take users to contact information for the speaker,begin an email to the speaker, contact the speaker on a chatapplication, or take any other action.

As another example, the transcript may be updated to reflect the joiningand leaving of participants or to reflect when certain data items werecreated, shared, modified, or otherwise accessed. Additionally, links tothe data items may be inserted into the transcript at the appropriatetime. If there is a chat log or other similar data in data items, thenthe chat log may be collated and included in the transcript, or madeaccessible from the transcript.

Event application 110 is programmed or configured to identify tasksassigned during an event and identify the participants to whom the taskwas assigned. The tasks assigned during an event may be identified froma transcript or from data items, including media data. The tasks may beidentified using any method, such as by natural language processing orusing keywords. For example, if a participant says, “Bill you need toget me this action item by Friday” a task for Bill may be “get actionitem by Friday.” A due date may or may not be associated with a task,depending, for example, on whether a due date was included with thetask. In the above example, the due date would be Friday. Onceidentified, the assigned tasks may be used to take other actions, asdiscussed below.

Event application 110 is programmed or configured to create new calendaritems. The new calendar items may be created for one particularparticipant or for any number of participants. The calendar items may becreated in any manner and for any reason. For example, if a participanthas a task assigned to them during an event, then a calendar item may becreated for that participant reminding them to complete their task bythe assigned date.

Alternatively, or in addition, other actions may be taken by eventapplication 110, such as creating an item or ticket in an issue trackingsystem, sending a notification or reminder, or any other suitableaction. As another example, if a transcript includes the organizer of ameeting saying, “lets schedule a follow-up on the 23^(rd),” then a newcalendar item may automatically be created on the 23^(rd) inviting allparticipants.

Event application 110 is programmed or configured to filter data items.The data items may be filtered in any way. The stringency of thefiltering may be adjusted by any suitable entity to ensure that onlyrelevant data items are used to update the calendar item or areotherwise shown to participants. The filtering may be based on thecontent of the data items, the time of creation or use of the data item,the source of the data item, the destination of the data item (whereapplicable), a security or clearance level associated with the dataitem, metadata, or any other attribute. In general, event application110 filters the data items to prevent irrelevant data items fromcluttering storage and calendar items and to not waste the time ofparticipants.

Event application 110 is programmed or configured to identifymodifications made to data items during the event. Optionally,modifications made to data items shortly before or after an event mayalso be identified. The modifications may be determined by comparing afirst version of the data item (such as when the data item was firststored) with a second version of the data item (such as when the dataitem was last stored). Alternatively, the modifications may bedetermined as the modifications are made to the data item, orfunctionality of a different application may be relied on to trackmodifications, such as a text editing application.

Due to the modifications, multiple versions of data items may becreated. Any number of versions may be created, such as an originalversion without modifications, a final version with modification, and adelta version that shows the modifications made. Any number of versionsof a data item may be stored and subsequently presented to theparticipants, as discussed below.

Event application 110 is programmed or configured to generate a summaryof the event. The summary may include highlights or other notablemoments from the event, such as tasks or action items assigned,conclusions reached, modifications to documents made, or any otheravailable data. The summary may include timestamps and links to orcopies of documents discussed. The summary may also include collatingthe stored data items or otherwise organizing the stored data items foreasier retrieval and subsequent use.

Event application 110 is programmed or configured to update calendaritems. The calendar items may be updated with any available information,such as data items, transcripts, and media data. The quantity of dataitems added to the calendar items may be adjusted by any suitable entityfor any reason. The update may include attaching copies of data items,transcripts, or media data to the calendar item, adding links to dataitems, transcripts, or media data to the calendar item, addingparticipants who attended but were not originally listed, removing ornoting participants who were invited but did not attend, including asummary, highlighting identified tasks and action items, or any otheritem.

Optionally, event application 110 may confirm or get approval from oneor more participants before updating the calendar items with data items.For instance, if a document was emailed between two participants duringan event, approval may be required from both participants beforeallowing the document to be shared with all participants. The parametersfor requiring approval before adding data items to a calendar item maybe based on any factor or factors, may be set by any suitable entity,and may be changed at any time.

Event application 110 is programmed or configured to send notifications.Notifications may be sent in any suitable manner or format, such as anemail message or a chat message. Notification may be sent to anyrecipient for any reason. For example, participants in an event may benotified when the calendar item has been updated with additional dataitems, media data, transcripts, and the like. A participant, whetherpresent in the event or not, who has been assigned a task may benotified of the task. Participants who were invited to the event butunable to attend may be notified of the results of the meeting, such asby sending a summary of the meeting or including all assigned tasks inthe notification.

In one embodiment, server computer 105 may execute additionalapplications (not shown) besides event application 110. The additionalapplications server computer 105 may execute may provide any of thefunctionality needed to create, use, modify, or otherwise accesscalendar item 120 or data item 125. Further, the additional applicationsserver computer 105 may execute may provide some of the functionalityneeded to process a data item 125, such as transcription, determiningmodifications to data items 125. Alternatively, as discussed above,event application 110, a third party, or other entity may provide thesefunctionalities.

In one embodiment, client device 130 may be any computing device,including, but not limited to: work stations, personal computers,general purpose computers, laptops, Internet appliances, hand-helddevices, wireless devices, wired devices, portable or mobile devices,wearable computers, cellular or mobile phones, portable digitalassistants (PDAs), smart phones, tablets, multi-processor systems,microprocessor-based or programmable consumer electronics, gameconsoles, set-top boxes, network PCs, mini-computers, and the like.Although not shown, client device 130 may communicate with data storagedevice 115 using any suitable method. Client device 130 may includeapplications, such as operating system software or application 135.Application 135 may be any application executing on client device 130 oraccessed by client device 130. Application 135 may be used by eventapplication 110 to provide some of the functionalities described above,such as by using a plugin, module, APIs, or other programmatic methods.

3. Example Functional Implementation

FIG. 2 shows an example flowchart of a method automatically detectingand storing data items associated with calendar items.

Although the steps in FIG. 2 are shown in an order, the steps of FIG. 2may be performed in any order and are not limited to the order shown inFIG. 2 . Additionally, some steps may be optional, may be performedmultiple times, or may be performed by different components. All steps,operations and functions of a flow diagram that are described herein areintended to indicate operations that are performed using programming ina special-purpose computer or general-purpose computer, in variousembodiments. In other words, each flow diagram in this disclosure is aguide, plan or specification of an algorithm for programming a computerto execute the functions that are described.

In step 200, a calendar item for an event is obtained. The calendar itemmay be obtained from a source such as a database or a client computingdevice. The calendar item may have originally been created at any timeby any application. Once obtained, data from the calendar item may beprocessed or otherwise extracted in any manner. The data may include,but is not limited to: a start date, a start time, an end date, an endtime, a location, a subject, zero or more attachments, reference(s)content in a message associated with the calendar item or content in thebody of the calendar item, invited participants, responses ofparticipants (such as yes, no, maybe), participant data such as firstname, last name, email address, phone number, chat handle, or any otherdata.

In step 205, a determination is made whether the event associated withthe calendar item has begun. The determination may be implemented byexecuting a continuous background process or daemon that tests, eachsecond for example, whether any calendar item stored in the system hasstarted. The determination may be made based on comparing data from thecalendar item, such as a start date and time, to values of a systemclock of the server computer or host on which an event application isexecuting. The determination may optionally be made a few minutes priorto a start time. Additionally or alternatively, the determination ofstep 205 may occur in response to a database trigger that has beenconfigured against a particular column of a database that is updatedwhen an event starts, where rows in a database table represent events,and the database table is managed in a database on data storage device115 or accessible to server computer 105 over one or more networks. Or,the determination of step 205 may be made in response to receiving aprogrammatic event, notification or call from another application orsystem. For example, referring to FIG. 1 , when a calendar item 120 isassociated with an event occurring in an application that is separatefrom the event application 110, then when the event starts, the otherseparate application may transmit a programmatic notification to theevent application specifying that the event started.

In an embodiment, if the event has started as indicated by the test ofstep 205, then the method proceeds to step 210. If the event has notstarted, then the method proceeds to step 280.

In step 210, a location associated with the event is accessed. Onepurpose of accessing the location is to permit collection of data items,content items, media data or references to them as the event isoccurring. The location may include multiple different locations, any ofwhich may comprise references to or identifiers of a phone conferencecall, a video feed, or a chat group. The location may be accessed byjoining a video conference or audio conference as the host or aparticipant, or via a computing device of a participant of the event.The location may be determined from location data obtained from mobilecomputing devices of participants, or from external sources of locationdata. Location data also can be obtained from inbound email. Thecollection of data item 125 or a reference to the data item may beexecuted in several ways depending on the nature of the event. In oneembodiment, the event application is programmed to detect that it, oranother application, is being used to present, display or use a dataitem, content item or media data. For example, the event application maydetect that a video conference application is being used to present adocument, share a document, or record a meeting. Detection may beimplemented using a listener process that programmatically hooks tointerrupt handlers or to an event bus of another application. Detectionalso may comprise transmitting a parameterized URL, functioning as aquery for data items, content items or media data that have been used,to a web service or to an online application that has implemented anAPI. Or, detection may comprise direct detection within the eventapplication that specific presentation, sharing or recording functionshave been invoked. Or, detection may comprise invocation of a functionof the event application using a database trigger that has beenconfigured on a column of a table in a database that represents theevent, in an event application that is programmed to update the columnwhen sharing a data item starts. Detection also may comprise detectingany digital data associated with a page, application etc. In anotherembodiment, the event application is programmed to detect that anotherapplication in use during the event is generating, presenting or sharinga data item. For example, a participant may exchange chat messages withothers, receive documents shared over chat, receive emails withattachments, or create whiteboard drawings captured on electronicwhiteboard application. In each case, the event application isprogrammed to detect the use of a data item, content item or media data,via a programmatic call, event listener process, interrupt handler orother programmatic connection to the other application, and to receive alink, identifier or copy of the data item, content item or media data inresponse. The other applications involved in these communications mayinclude chat room applications, task management applications, issuetracking applications, incident management applications, projectplanning applications, email applications, drawing or graphicsapplications, word processors or collaborative document managementsystems, implemented as online web-based or SaaS applications and/ordesktop applications.

In step 215, the participants who are present are determined. Step 215may be performed continuously, or at regular intervals, until the eventis over, so that any participants who leave early or join late may alsobe identified. In one embodiment, participants are identified byobtaining an account identifier, user identifier, handle or otheridentifier of a user or machine from an application program that managesthe event. As one example, determining participants may comprise theevent application accessing a list of user identifiers or accountidentifiers of users or accounts who are then currently logged into theevent application and comparing those identifiers to the identifiers ofparticipants who were invited to an event or included in a calendaritem.

For another example, with a video conference, the event application maybe programmed to query the video conference application with a requestto report the identifiers of each user or account that has joined aparticular video conference call, starting at the start time of the calland repeatedly at intervals during the call; one approach is to transmita query each minute during the call to obtain a list of accountidentifiers or user identifiers for all participants that are thencurrently on the call. In one embodiment, the account identifiers oruser identifiers that are obtained in this manner are added to acumulative list, so that all participants who joined the call for atleast one minute are captured in an event record. The use of acumulative list permits collecting data items from all participants inan event even if one or more participants leaves the event before itends.

In some embodiments, location services of mobile computing devices ofparticipants may be used to report then-current locations of mobileparticipants. For example, FIG. 2 may be implemented in part using anapplication program or app for local installation on individual mobilecomputing devices of participants. When participants use the mobile appon a mobile device to join an event, the mobile app may query a locationservice of the operating system of the mobile device and report locationdata as part of step 215.

In step 220, media data and data items from the event are detected andstored, either as references or links, or as copies. Media data mayinclude a video recording, an audio recording, chat logs, and the like.Data items may include any electronic file or other digital data that iscreated, modified, shared, used, or otherwise accessed during the event.Examples of data items include, but are not limited to: URLs, a website,emails, chat logs, a text or SMS message, an audio recording, a videorecording, a transcript, a text document, a spreadsheet, source code, aslide presentation or deck, a slideshow, pictures or other images,electronic data file(s), metadata, etc. Obtaining links or copies may beimplemented using programmatic calls to other applications, orparameterized URLs that are transmitted as queries to web services, orby directly obtaining a link to a resource that was specified or usedwithin the event application.

Optionally, data items that are created, modified, shared, used, orotherwise accessed within a specified amount of time before or after theevent may also be detected and stored. The specified amount of time maybe stored as configuration data and updated using administrativefunctions of the event application. The media data and data items may bestored using object references, pointers, links, URLs, URIs or copies inany of a database a repository system, or a publicly or privatelyaccessible server or any combination thereof. Copies of the media dataand data items may be stored, or links to locations where the media dataor data items may be stored, depending on preferences and settings.

In step 225, a determination is made whether the event has ended. Thedetermination may be based on an end time of the calendar data item, ormay be determined based on when most, or all, of the participants haveleft the location associated with the event. Or, the determination mayoccur in response to a programmatic call, interrupt, or other signalfrom another application or within the event application. Or, thedetermination may occur in response to invocation of code in the eventapplication from a database trigger that is configured on a column of atable in a database that represents the event and that is updated whenthe event ends. If the event has not concluded, the method returns tostep 220 and continues to detect and store media data and data items. Ifthe event has concluded, the method proceeds to step 230.

In step 230, the stored media data and data items are processed toextract information from the items or to use them to improvedistribution efficiency. As indicated by the dotted lines, theindividual steps within step 230 may be performed in parallel or atdifferent times, by different computing devices or the same computingdevice, and using different applications, a single application, athird-party service, or any combination thereof. Further, each of thesteps within step 230 are optional, and may or may not be performeddepending on settings, what data items were stored, what media data wasstored, or any other factor. Generally, upon completion of processingrelevant media data and data items have been identified and/or createdso that the calendar item maybe updated with the relevant information instep 270. In an embodiment, the event application 110 (FIG. 1 ) isprogrammed to perform one or more of the steps within step 230 basedupon configuration data or by options selected by a user oradministrator.

In another embodiment, step 230 may comprise automatically tracking, viaclickstream data or other data representing actual user interaction withapplications or devices, the activity of participants and using theactivity data to identify resources to associate with an event. Forexample, clickstream data may indicate launching an application such asa word processor, presentation application or media player, andaccessing a particular file; in response, data identifying the fileand/or application may be associated with the event.

In step 235, media data is transcribed to generate a transcript. Anymedia data may be used to generate a transcript, such as a videorecording, an audio recording, or a combination thereof. The transcriptmay be generated in any manner, such as by a transcription application,utilizing a third-party transcription service, or any other method. Thegenerated transcript may include added information, such asidentification of speakers, whether by actual name or by genericidentification (such as male voice, female voice, speaker1, speaker2,etc.).

In step 240, the transcript is updated. The transcript is updated usingavailable information from the media data, data items, and calendaritem. Any data may be added to the transcript to enrich and improve theusability of the transcript. For example, participant data from thecalendar item or other sources may be used to update or correct thenames of speakers in the transcript. The names of speakers can also beupdated to clickable links that direct users to a chat message or emailmessage addressed to the speaker. As another example, if there are chatlogs, the chat logs or content of the chat logs could be included andcollated with, or otherwise made accessible from, the transcript.

Additionally, any shared data items could be noted when the data itemwas detected, and a link provided to access the associated data item.Timestamps for when participants joined or left may also be added. Thus,the transcript becomes immensely more useful as the entire context ofthe event is made evident and accessible from the transcript. Any otherupdates may be made and any available data may be used to update thetranscript.

In step 245, tasks assigned to participants are identified. Optionally,the participants may be notified. The tasks may be identified from mediadata, a transcript, a chat log, data items, and/or any other source. Thetasks may be identified using natural language processing, keywords, orany other method. In addition to identifying tasks, the participantassociated with the task, as well as a due date (when applicable) mayalso be identified. The identified tasks, participants, and due datesmay be stored in any suitable location in any manner or format.

Furthermore, in an embodiment, the process of FIG. 2 is programmed totransfer data for tasks to other processes in addition or as analternative to updating a meeting object. For example, task data may becopied to a master page that records all meetings of a particular userfor a period. Or, the process of FIG. 2 may be programmed to trigger anauditing operation, an archiving operation, an issue tracking operationor other process or workflow based on the task data. In this manner, theprocess of FIG. 2 is programmed to make a meeting part of a largerworkplace ecosystem or a larger federated productivity application set,by using meeting data and exporting it to other applications to launchactions of those applications.

In step 250, new calendar items are created and/or the process triggersor takes action with other applications or systems. For example, a newcalendar item may be created for a particular participant, for asubgroup of participants, or all participants. Any number of newcalendar items may be created. The calendar items may be created basedon the tasks identified in step 245. For example, if a task was assignedto Jane that was due Tuesday, a new calendar item may be created forTuesday morning to remind Jane of the task. As another example, calendaritems may be created based on data besides the tasks identified in step245, such as directly from the transcript, media data, chat logs, orother source. For example, if someone says “ . . . schedule a follow-upmeeting in a week,” a new calendar item may be created for next week asthe follow-up. Alternatively, any other source or reason may be used tocreate new calendar items.

In some embodiments, step 250 may comprise executing API calls,executing other programmatic calls, transmitting data and/or triggeringaction by other applications. Examples of triggering action may includecreating issues in an issue tracking system; creating tasks in aproductivity application; or creating lists in a document managementsystem. API calls or other programmatic calls may include any of thecollected data items, or links or references, as payloads or parameters.

In step 255, collected data items are filtered. The collected data itemsmay be filtered in any manner using any method. The data items arefiltered to reduce irrelevant data items and to present participantswith the data items that are most likely to be relevant. Further, thefiltering increases the privacy of the participants by removingirrelevant data items. Any parameters may be used to filter the dataitems, and the parameters of the filtering may be adjusted at any timeby any suitable entity.

In step 260, modifications made to data items during the event areidentified. The modifications may be identified in any manner. Themodifications may be identified by comparing a first version of a dataitem, such as when the data item was first stored, with a second versionof the data item, such as when the event ended or when the data item wasno longer in use during the event. Alternatively, the modifications maybe identified as the modifications are made, such as by relying onanother application to track the modifications. As part of identifyingmodifications, multiple versions of data items may be used or created,such as a first version without modifications, a second version withmodifications, and a delta version that identifies the changes made.

In step 265, a summary of the event is generated. The summary of theevent may be generated using any stored or otherwise availableinformation, including transcripts, media data, data items, and calendaritems. The summary may be generated in any manner, such as throughnatural language processing or other methodologies. The summary may beof any length and settings associated with the summary, such as lengthor types of information included, may be set at any time by any suitableentity.

In step 270, the calendar item is updated with media data, data items,transcripts, summaries, and/or other data from the event. Any amount ofdata from the event may be used to update the calendar item. Thecalendar item may be updated in any way, such as by modifying thesubject or body of the calendar item, adding attachments, adding links,removing participants, adding participants, and any combinationsthereof.

In step 275, notifications are sent. Step 275 is optional, and may notbe performed. The notifications may be sent for any reason, in anymanner or format, to any recipient. For example, notifications may besent to alert participants that the calendar item has been updated. Asanother example, notifications may be sent to invited participants whowere unable to attend, so that they may determine what happened at theevent.

In step 280, the method waits until the event begins, and returns to thedetermination at step 205.

Using the above method, the usability and efficiency of calendaring,scheduling, and events may be vastly improved. Events may be streamlinedand made more productive. For example, there may no longer be a need totake notes during an event, since a transcription or summary may beprovided. Further, because tasks or action items may be identified, theresults of the event may be dramatically improved as participantsremember what they are supposed to do and follow through quicker.

Additionally, the calendar item itself becomes a meaningful tool for aparticipant to remember what transpired during an event because theentire context of the event is made accessible by updating the calendaritem to include data items, transcripts, media data, etc. In contrast,“traditional” calendar items are static and provide no assistant to aparticipant attempting to remember what transpired during an event.Further, the above method may reduce the usage of computing power,memory, and/or bandwidth by consolidating data items and making the dataitems easily available to participants. Further, the overall usabilityand functionality of the computing device and associated applications isalso greatly increased.

4. Implementation Example

FIG. 3 illustrates an example calendar item from a method forautomatically detecting and storing data items associated with calendaritems.

FIG. 3 shows a calendar item before an event begins and after the eventhas concluded and the calendar item has been updated. In this example,the event is a work meeting that was conducted using a video conference.Unfortunately, one of the original participants—Jenny—was unable toattend the meeting but sent Ashley, a coworker, in her place. During themeeting, a chat application was used to send a few messages and shareURLs that were discussed. Additionally, multiple text documents wereshared, discussed, and modified, emails were sent, and Jim was assigneda task.

Calendar item 300 shows the original calendar item with basicinformation. The subject of the meeting is identified as “DiscussProject ABC,” and a time and date for the meeting are identified:“August 13^(th) at 2:00 pm.” Additionally, Video Conference Room A isidentified as the location (and a link is provided to access the videoconference itself), and the four participants are identified by theiremail addresses: John, Sarah, Jim, and Jenny. Without using the methodsdiscussed in this document, after the meeting concluded calendar item300 would not be updated, and would simply sit on the participantsrespective calendars. If John, Sarah, Jim or Jenny (who was replaced byAshley) needed to remember what the outcome of the meeting was, theywould need to rely on their own notes or memories. Jim forgets the taskassigned to him during the meeting and the overall results of themeeting were mediocre at best. Another meeting will need to be held.

In sharp contrast to the above, updated calendar item 305 has beenupdated using event application 110 and the methods discussed in thisdocument, and provides the full context and results of the meeting. Thisgreatly improves the efficiency, functionality, and usability ofcalendaring and scheduling applications and for events or meetings aswell. Updated calendar item 305 is updated after the conclusion of themeeting. In updated calendar item 305, the participant list has beenupdated to reflect the fact that Jenny was unable to attend, and Ashleyattended in her place.

Further, updated calendar item 305 now includes summary 310, transcript315, data items 320, video recording 325, and chat log 330. Summary 310was generated using transcript 315, data items 320, and chat log 330.Summary 310 includes a brief summary of the meeting, and identifies thetask assigned to Jim. Transcript 315 includes a complete transcript ofthe meeting, and was generated using video recording 325. Transcript 315has also been updated to accurately identify each speaker, and to allowthe names of speakers to be clicked to easily send that person a chatmessage. Further, transcript 315 identifies when data items 320 wereshared, and links to the associated data items are provided.

Data items 320 are the data items shared during the meeting. Multipleversions of each data items 320 are included, so that the originalversion, final version, and the modifications made during the meetingare easily accessible. Video recording 325 is a recording of the videoconference. Chat log 330 is a log of the chat that occurred during themeeting.

It will be apparent that the techniques of this disclosure providenumerous benefits including reducing the use of computer CPU cycles,storage, memory and network bandwidth that otherwise would be consumedfor multiple participants in an event to request and obtain copies orreferences to data items that were accessed, shared or presented duringthe event. As one specific example, after a video conference that wasscheduled in a calendar item with multiple participants using a calendarapplication, and in which one participant has shared a set ofpresentation slides that are stored in a file or deck, there is no needfor the participant to e-mail a copy of the deck to all otherparticipants. Instead, the techniques of this disclosure make itpossible for the calendar application to automatically access thepresentation and to associate a link or copy with an updated version ofthe calendar item. Consequently, after the video conference, anyparticipant may access the updated version of the calendar item torapidly obtain the presentation.

5. Implementation Example—Hardware Overview

According to one embodiment, the techniques described herein areimplemented by one or more special-purpose computing devices. Thespecial-purpose computing devices may be hard-wired to perform thetechniques, or may include digital electronic devices such as one ormore application-specific integrated circuits (ASICs) or fieldprogrammable gate arrays (FPGAs) that are persistently programmed toperform the techniques, or may include one or more general purposehardware processors programmed to perform the techniques pursuant toprogram instructions in firmware, memory, other storage, or acombination. Such special-purpose computing devices may also combinecustom hard-wired logic, ASICs, or FPGAs with custom programming toaccomplish the techniques. The special-purpose computing devices may bedesktop computer systems, portable computer systems, handheld devices,networking devices or any other device that incorporates hard-wired orprogram logic to implement the techniques.

For example, FIG. 4 is a block diagram that illustrates a computersystem 400 upon which an embodiment of the invention may be implemented.Computer system 400 includes a bus 402 or other communication mechanismfor communicating information, and a hardware processor 404 coupled withbus 402 for processing information. Hardware processor 404 may be, forexample, a general-purpose microprocessor.

Computer system 400 also includes a main memory 406, such as arandom-access memory (RAM) or other dynamic storage device, coupled tobus 402 for storing information and instructions to be executed byprocessor 404. Main memory 406 also may be used for storing temporaryvariables or other intermediate information during execution ofinstructions to be executed by processor 404. Such instructions, whenstored in non-transitory storage media accessible to processor 404,render computer system 400 into a special-purpose machine that iscustomized to perform the operations specified in the instructions.

Computer system 400 further includes a read only memory (ROM) 408 orother static storage device coupled to bus 402 for storing staticinformation and instructions for processor 404. A storage device 410,such as a magnetic disk or optical disk, is provided and coupled to bus402 for storing information and instructions.

Computer system 400 may be coupled via bus 402 to a display 412, such asa cathode ray tube (CRT), for displaying information to a computer user.An input device 414, including alphanumeric and other keys, is coupledto bus 402 for communicating information and command selections toprocessor 404. Another type of user input device is cursor control 416,such as a mouse, a trackball, or cursor direction keys for communicatingdirection information and command selections to processor 404 and forcontrolling cursor movement on display 412. This input device typicallyhas two degrees of freedom in two axes, a first axis (e.g., x) and asecond axis (e.g., y), that allows the device to specify positions in aplane.

Computer system 400 may implement the techniques described herein usingcustomized hard-wired logic, one or more ASICs or FPGAs, firmware orprogram logic which in combination with the computer system causes orprograms computer system 400 to be a special-purpose machine. Accordingto one embodiment, the techniques herein are performed by computersystem 400 in response to processor 404 executing one or more sequencesof one or more instructions contained in main memory 406. Suchinstructions may be read into main memory 406 from another storagemedium, such as storage device 410. Execution of the sequences ofinstructions contained in main memory 406 causes processor 404 toperform the process steps described herein. In alternative embodiments,hard-wired circuitry may be used in place of or in combination withsoftware instructions.

The term “storage media” as used herein refers to any non-transitorymedia that store data or instructions that cause a machine to operationin a specific fashion. Such storage media may comprise non-volatilemedia or volatile media. Non-volatile media includes, for example,optical or magnetic disks, such as storage device 410. Volatile mediaincludes dynamic memory, such as main memory 406. Common forms ofstorage media include, for example, a floppy disk, a flexible disk, harddisk, solid state drive, magnetic tape, or any other magnetic datastorage medium, a CD-ROM, any other optical data storage medium, anyphysical medium with patterns of holes, a RAM, a PROM, and EPROM, aFLASH-EPROM, NVRAM, any other memory chip or cartridge.

Storage media is distinct from but may be used in conjunction withtransmission media. Transmission media participates in transferringinformation between storage media. For example, transmission mediaincludes coaxial cables, copper wire and fiber optics, including thewires that comprise bus 402. Transmission media can also take the formof acoustic or light waves, such as those generated during radio-waveand infra-red data communications.

Various forms of media may be involved in carrying one or more sequencesof one or more instructions to processor 404 for execution. For example,the instructions may initially be carried on a magnetic disk orsolid-state drive of a remote computer. The remote computer can load theinstructions into its dynamic memory and send the instructions over atelephone line using a modem. A modem local to computer system 400 canreceive the data on the telephone line and use an infra-red transmitterto convert the data to an infra-red signal. An infra-red detector canreceive the data carried in the infra-red signal and appropriatecircuitry can place the data on bus 402. Bus 402 carries the data tomain memory 406, from which processor 404 retrieves and executes theinstructions. The instructions received by main memory 406 mayoptionally be stored on storage device 410 either before or afterexecution by processor 404.

Computer system 400 also includes a communication interface 418 coupledto bus 402. Communication interface 418 provides a two-way datacommunication coupling to a network link 420 that is connected to alocal network 422. For example, communication interface 418 may be anintegrated services digital network (ISDN) card, cable modem, satellitemodem, or a modem to provide a data communication connection to acorresponding type of telephone line. As another example, communicationinterface 418 may be a local area network (LAN) card to provide a datacommunication connection to a compatible LAN. Wireless links may also beimplemented. In any such implementation, communication interface 418sends and receives electrical, electromagnetic or optical signals thatcarry digital data streams representing various types of information.

Network link 420 typically provides data communication through one ormore networks to other data devices. For example, network link 420 mayprovide a connection through local network 422 to a host computer 424 orto data equipment operated by an Internet Service Provider (ISP) 426.ISP 426 in turn provides data communication services through theworld-wide packet data communication network now commonly referred to asthe “Internet” 428. Local network 422 and Internet 428 both useelectrical, electromagnetic or optical signals that carry digital datastreams. The signals through the various networks and the signals onnetwork link 420 and through communication interface 418, which carrythe digital data to and from computer system 400, are example forms oftransmission media.

Computer system 400 can send messages and receive data, includingprogram code, through the network(s), network link 420 and communicationinterface 418. In the Internet example, a server 430 might transmit arequested code for an application program through Internet 428, ISP 426,local network 422 and communication interface 418.

The received code may be executed by processor 404 as it is received, orstored in storage device 410, or other non-volatile storage for laterexecution.

What is claimed is:
 1. A computer-implemented method comprising:obtaining a digital calendar item for an event, the digital calendaritem comprising time data, location data, and participant data forparticipants invited to the event; evaluating the time data to determinethat the event has begun; in response to determining that the event hasbegun, determining, using at least one of audio data, video data, orchat data generated during the event, which of the participants arepresent for the event; in response to creation of a media data objectcomprising one or more of the video data, audio data, and the chat dataof the event, obtaining a transcript of the media data object;identifying from the transcript that a task is associated with aparticipant of the participants that were present for the event; and inresponse to the identifying that the task is associated with theparticipant: generating an issue in an issue tracking system; assigningthe participant to the issue in the issue tracking system; and updatingthe digital calendar item to include a reference to the issue.
 2. Thecomputer-implemented method of claim 1, wherein assigning theparticipant to the issue comprises: identifying that the task wasassigned to the participant comprises: generating a calendar item forthe issue; and sending the calendar item to an account associated withthe participant.
 3. The computer-implemented method of claim 1, furthercomprising: analyzing the transcript to identify a deadline forcompleting the issue; and creating an issue deadline based on theidentified deadline.
 4. The computer-implemented method of claim 1,further comprising in response to identifying that the task isassociated with the participant: identifying an existing issue in theissue tracking system; and assigning the participant to the existingissue in the issue tracking system.
 5. The computer-implemented methodof claim 4, wherein, in response to assigning the participant to theexisting issue, sending a notification to other accounts associated withthe issue that the participant has been assigned to the issue.
 6. Thecomputer-implemented method of claim 1, wherein identifying the taskcomprises: analyzing the transcript of the media data object to identifya subject discussed during the event; determining that the subjectcorresponds to an action to be taken by one or more of the participantsof the event; and determining an identification of the participantsassociated with the action.
 7. The computer-implemented method of claim1, further comprising generating an API call to the issue trackingsystem, the API call comprising a request to generate the issue at theissue tracking system.
 8. The computer-implemented method of claim 7,wherein the API call comprises an identification of the participant. 9.The computer-implemented method of claim 7, further comprising: inresponse to the issue being generated at the issue tracking system,receiving an issue identification from the issue tracking system; andupdating the digital calendar item to include the issue identification.10. A computer-implemented method comprising: monitoring a videoconferencing service to determine that a video conference has begun; inresponse to determining that the video conference has begun, monitoringelectronic chat messages entered into a chat function of the videoconferencing service, the electronic chat messages received from clientdevices associated with participants of the video conference; analyzingthe electronic chat messages to identify a potential task included in achat message of the electronic chat messages; in response to identifyingthe potential task: determining a participant associated with thepotential task; causing a productivity application to create an issue;and assigning the participant to the issue; and sending an electronicnotification to a digital account associated with the participant, theelectronic notification indicating that the issue has been created andassigned to the participant.
 11. The computer-implemented method ofclaim 10, wherein sending the electronic notification to the digitalaccount associated with the participant comprises: generating a calendaritem for the issue; and sending a calendar invite to the digital accountassociated with the participant.
 12. The computer-implemented method ofclaim 11, further comprising analyzing the electronic chat messages,transcript data, or a combination thereof to identify a date associatedwith the issue, wherein causing the productivity application to createthe issue comprises assigning the issue a due date associated with theidentified date.
 13. The computer-implemented method of claim 12,wherein generating the calendar invite comprises referencing the duedate in the calendar invite.
 14. The computer-implemented method ofclaim 10, wherein determining the participant associated with thepotential task comprises identifying a participant identification thatwas referenced by the chat message.
 15. The computer-implemented methodof claim 10, wherein determining the participant associated with thepotential task comprises analyzing the chat message to identify aparticipant identification included in the chat message.
 16. Thecomputer-implemented method of claim 10, further comprising: generatinga summary of the video conference, the summary including the issue andthe participant assigned to the issue; and updating a calendar item toinclude the summary.
 17. A computer-implemented method comprising:evaluating a digital calendar item for an event to determine that theevent has begun; in response to determining that the event has begun,determining, using at least one of call data, video data, or chat datagenerated during the event, a list of participants that are present forthe event; determining that a document stored at a collaborativedocument management system was shared during the event; determining thatthe document was edited during the event; in response to determiningthat changes were made to the document during the event: updating thedocument at the collaborative document management system in accordancewith the changes made during the event; and updating the digitalcalendar item to include the updated document; and sending an electronicnotification to digital accounts associated with one or moreparticipants in the list of participants, the electronic notificationindicating that the document was updated at the collaborative documentmanagement system.
 18. The computer-implemented method of claim 17,wherein the electronic notification comprises a link to the document inthe collaborative document management system.
 19. Thecomputer-implemented method of claim 17, further comprising, in responseto determining that the document was edited during the event, generatinga list of changes made to the document, wherein the electronicnotification comprises the list of changes.
 20. The computer-implementedmethod of claim 17, wherein updating the document at the collaborativedocument management system comprises making an API call to thecollaborative document management system, the API call comprisingchanges made to the document during the event.